Understanding database recovery

TeamWork is capable of complete recovery of the Hypertrieve database, although the chances of corruption are very limited due to the transaction-oriented structure. Three levels of database recovery are possible with the Hypertrieve database engine. Each level takes advantage of a snapshot of the database that is made:

• When a Prepare for Backup operation occurs
• On demand as controlled by the MaximumLogSize and MinimumSnapshotInterval settings described in Configuring the MaximumLogSize setting and Configuring the MinimumSnapshotInterval setting.

When a snapshot is created, the transaction log files are committed to the active database and the database is copied as the snapshot file. The transaction log file is then reset (truncated).

The three levels of database recovery are described in the following topics.